home *** CD-ROM | disk | FTP | other *** search
Text File | 1989-10-16 | 1.9 KB | 55 lines | [TEXT/GEOL] |
- Item 6759500 16-Oct-89 11:09
-
- From: D1282 Power Up,PRT
-
- To: SCHMUCKER1 Schmucker, Kurt
- MACAPP.TECH$ MACAPP Tech
-
- Sub: Eiffel
-
- Attn: Schmucker, Kurt
- Attn: MacApp.Tech$
- SentBy: James Plamondon
- Date 10/16/89
- Subject Eiffel
- From James Plamondon
- To Schmucker, Kurt
- CC MacApp.Tech$
-
- Reply to: Eiffel
- I appreciate your comments on Eiffel and Meyer. I am interested particularly
- in your statement, "If you can get to MacApp from Eiffel, I will give it a
- very serious look. If you can't, I will give it a glance. "
-
- This implies that you view the use of MacApp as an end, not as a means to an
- end — the latter ‘end’ being the rapid production of quality software. I
- wholeheartedly agree that the use of MacApp is the best existing means of
- application development on the Macintosh today. But for how long can this
- continue to be the case? Even the release of C++ threatens MacApp. It won’t
- take C++ programmers long to get frustrated with MacApp’s Object Pascal
- heritage — specifically MacApp’s file structure and its lack of multiple
- inheritance (although I gather that the use of multiple inheritance is
- restricted in MPW C++).
-
- I would suggest that if the rapid production of quality software is the end,
- and not the use of MacApp, then any language, product, or tool that may be a
- means to this end deserves a serious look, whether it supports MacApp or not.
- Wouldn’t you agree?
-
- I use MacApp today, because it is the best existing tool for the job. But I
- disagree vehemently with the motto of MADA — that “The Future is MacApp.”
- MacApp is not the future; MacApp is the present — the future has yet to come.
-
- Respectfully,
-
-
- James Plamondon
- Software Engineer
- PowerUp! Software
- 2929 Campus Drive, Suite 300
- San Mateo, CA 94403
- (415) 345-5900 x351
- AppleLink: D1282
- CompuServe: 71230,734
-
-